|
Domain Inventory is a design pattern, applied within the service-orientation design paradigm, whose application enables creating pools of services, which correspond to different segments of the enterprise, instead of creating a single enterprise-wide pool of services. This design pattern is usually applied when it is not possible to create a single inventory of services〔(Service Inventory )〕 for whole of the enterprise by following the same design standards across the different segments of the enterprise. The Domain Inventory Design pattern by Thomas Erl asks, "How can services be delivered to maximize recomposition when enterprise-wide standardization is not possible?" and is discussed as part of this (podcast ). ==Rationale== As per the guidelines of the Enterprise Inventory design pattern, it is beneficial to create a single inventory that spans the whole of the enterprise as it results in services that are more standardized, interoperable and easily composable. However, there may be situations when a single enterprise-wide inventory cannot be created. This could be because of a number of reasons including: * management issues e.g. who will own the services and who will be responsible for their maintenance? * the organization is spread across different geographic locations. * different segments of the organization are supported by different IT departments and the technologies used are not the same. * some segments of the organization might not be ready for transition towards service-orientation. * a pilot project needs to be undertaken just to ascertain the effectiveness of SOA. * as per the guidelines of the Standardized Service Contract, it may be very difficult to create standardized data models across the enterprise. * cultural issues, e.g. IT managers not willing to give up control they have over the way different projects are developed. Considering the above-mentioned factors, it is rather more practical to build smaller groups of services whereby the scope of a group relates to a well-defined domain boundary within the enterprise.〔Mauro et al. (Standardized Device Services – A Design Pattern for Service Oriented Integration of Medical Devices ) (). Date accessed: 7 April 2010〕 This is exactly what is advocated by the Domain Inventory〔(Domain Inventory design pattern )〕 design pattern. By limiting the scope of a service inventory, it becomes easier to develop and manage a group of related services.〔Mauro. et al. (Service Oriented Device Integration - An Analysis of SOA Design Patterns. ) (), pp.1-10, 2010 43rd Hawaii International Conference on System Sciences, 2010. Date accessed: 7 April 2010.〕 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「Domain inventory pattern」の詳細全文を読む スポンサード リンク
|